Thanks for checking. Was worth a try but unfortunately not the problem apparently ... View more

I don't have a similar machine to compare so not sure but that line does worry me that indeed the GPU is not playing at all consistent with your observations. This machine should be at least as fast as that M4 Pro you compare to. I would reinstall the GPU driver and disable any custom settings on the GPU you might have done. Make sure you use the studio driver from NVidia and not the gaming one. From the system listing above you probably have the very latest version installed but good to check. ... View more

At the risk of sounding pedantic but have you tried hitting the "I" key on your keyboard or doing a command-I. I have noticed that sometimes, the info overlay doesn't show even when it is checked in the dialog. Pressing I a few times will bring it back. ... View more

There is also this notice in the lower section:  GPUDeviceEnabled: false It looks like the GPU is getting disabled more deeply somehow.  ... View more

Check out Jeffrey friedls collection publisher plugin: https://regex.info/blog/lightroom-goodies/collection-publisher ... View more

You have a lot of third-party plugins installed. I would try disabling them all and seeing if it still does the slowdown. If that helps, reenable the plugins one-by-one until you get the slowdown again. You really should see zero difference in performance with the new denoise vs the old one but the denoise data is stored very differently in the catalog in the new version and any plgins that scan and work with the catalog data might pose an issue.  Otherwise a cause might be that you have some antivirus software installed (not really needed on Mac OS because of the built-in AV software and different security model) that constantly scans the catalog.  ... View more

That looks like a graphics card(GPU) problem. Make sure your GPU drivers (if you're on windows) are up to date by going to the manufacturer's website and downloading the latest drivers. That usually fixes these kind of issues except for some older graphics cards such as Radeon cards that have this issue. So please post the relevant part of the system info dialog (help menu) to see what card you have. It can also be a problem with the monitor color profile. ... View more

That sounds like a gpu driver issue as others noted. The GPU you have should be fine but driver might need to be updated.  ... View more

If that solution (moving all into a new catalog) worked you have a bloated original catalog file. You might simply need to check the integrity of the original catalog and to optimize it. Hold your option key while restarting classic and select the original catalog in the dialog you get and hit the checkbox to check and optimize. That might help.  if you go with this new catalog, relinking to the cloud might go just fine but it might also duplicate everything you have in the cloud. Hard to predict. ... View more

What gpu do you have in that computer? Lightroom nowadays is very dependent on having a strong gpu. It will run slow even on machines with a fast processor and lots of memory if the gpu is underpowered. This is especially true if you use any of the ai features. ... View more

If you hold down the option key when starting classic, you'll get a dialog where you can check the integrity of a catalog file. Might be worth trying. If none of that works you might need to recover from a catalog backup. If you have a really hard deadline, you can always just create a new empty catalog and do your work in there. ... View more

This happens if you have a mask defined or are using one of the adaptive profiles (which creates masks in the background). Just recalculating the ai masks (there is a little circular icon you should see near the histogram in Classic) should fix these ghosts.  ... View more

The behavior for raw+jpeg is set in the preferences. There is a setting to treat jpeg next to raw as separate. It is indeed possible that your catalog has both raws and JPEGs as separate images in the same catalog folder and your Lightroom settings are set to not treat them as separate upon import. This might indeed make synchronize think the files are missing because it sees them as if they are a single raw+jpeg pair. I have never tried this but yeah try changing the setting for raw+joeg. ... View more

As already mentioned, you are going to need a new computer to be able to run the current versions of Lightroom and Mac OS that will allow you to open those files unfortunately. It is possible to trick Mac computers to install newer Mac OS versions by using openCore Legacy Patcher which is probably much further than most people are willing to go as it is definitely an advanced hack. ... View more

You will lose the ability to denoise a dng image if it is a HDR merge, a panorama merge, or if it was exported using the lossy compression option. It is also possible that it originally was a raw image shot at reduced resolution in camera. That also creates a linearized raw file. If that later gets converted to dng, you would not be able to denoise that image. ... View more

Not sure what you mean the new tool works exactly like the old slider but now you can live change the amount of denoise instead of having to generate a new dng file. The slider is exactly the same. 50 means half the full effect, 100 means maximum effect. Just like it did before. Just no new file needs to generate. ... View more

try creating a new catalog and import a few images. See if that is still slow. It appears you have been upgrading this catalog since Lightroom version 5 so perhaps some problems slipped in. ... View more

it would make the slider incredibly slow to respond if they didn't store the denoise data as every time it would need to recreate it. The data it stores is a reduced representation of the raw data as seen by the ai. The cool thing is that doing it this way allows them to on the fly dial in different denoise levels. Secondly, when you turn on xmp backups, what Lightroom Classic does is store the exact same data in the xmp sidecar backup as it stores in the catalog files. So this also includes this fast denoise data. This is no different from all the AI masks, AI remove data, etc etc. that all gets stored in the xmp sidecar if you enable the auto xmp writing even if Lightroom or camera raw could easily regenerate those masks. This can make the xmp sidecars really big indeed. ... View more

Are you sure the xmp files don't get actually updated when you are stepping through? Finder can be extraordinarily sluggish with updating the metadata columns. It certainly seems like Lightroom is saving something seeing how long it takes to count down the number of saves left. Often you have to close and reopen a folder to see any updates.  Anyway, these are clearly bugs with the automatic xmp writing system. That has always been very buggy unfortunately.   ... View more

Normally the denoise result is put in the catalog only. It only gets put as a copy in the xmp when you have automatic xmp writing turned on. This data has to reside somewhere. In previous versions of Lightroom, a separate dng file would get created with the denoise data. In the new version, the denoise data that allows you to charge the amount of denoising after the fact is stored in the metadata in the catalog. Denoising this way unavoidably adds some megabytes that have to be somewhere. ... View more

The way to work is exactly the same as if Classic is the master. Classic simply ALWAYS works as if it is the master of the universe. SO when you want to occasionally use CLassic, know that it will ALWAYS download everything new from the cloud. So be prepared to always have a full copy of everything in the cloud in your Classic catalog if you go this way. There really are only two options when involving the cloud. One go full Lightroom Cloudy and never use Classic again. 2. use Classic as the master, import in Classic and sync smart previews or import in Cloudy on mobile or Desktop, and be prepared that everything always will get downloaded to Classic.  You really cannot use Classic just a bit. It won't work that way. ... View more

>My LrC also says the lens correction is applied but it really hasn't. So - are you sure the lens correction is applied correctly?   Turns out you are right. It is applying the lens correction incorrectly. I could only really see that by comparing the merge from the full res images to the merge from the reduced res images as you can see below (HDR gets blown out in screenshots. The window actually has all the detail when viewed on my display) It is correcting but only partially which you can see by toggling the correction on and off. Sorry for missing this initially. This is clearly a bug indeed. Just directly merging to HDR is much faster for me but that might depend a lot on your hardware and might not be a solution for you. ... View more

P.S. I timed what it takes to export, reimport and convert to HDR vs just creating HDR directly and it is faster to just create the HDR from the original files:   Reduce size by export to dng using a export preset-> automatic reimport -> merge to HDR: 35 seconds Direct merge to HDR: 13 seconds   The actual process is faster for the direct merge but I counted the right click to get to the HDR dialog.   Now I tested this I can see that you are right that even though the interface says it is correcting for the lens distortion and vignette, it isn't actually doing that for the reduced size export image. It seems to only correct about 50% of the distortion! So there might be a bug here indeed. That said, just doing it from the orginal raf files is a lot faster anyway so that is what you should do. Interestingly if you merge to HDR using the raf files and then export to reduced size dng from there, the lens correction is correctly applied to the final file, so this is indeed some kind of effect from the merging to HDR using reduced-size dng files.   It will be even faster if you have a folder full of brackets and just select all -> enhance-> merge to HDR and it will automatically merge all HDR brackets. ... View more

Thanks, I tried to reproduce. I imported these three raf files. Exported them to lossy dng v16 with long side at 3000 pixels to same folder with automatic reimporting them to the catalog. Hit create HDR on the new files and the result came in fully corrected with the lens correction set correctly as you can see in screenshot below LR Classic 14.3.1 on MacBookPro M1 Max.  This seems to work correctly on my machine at least with the release version of Classic. Also tried this in Cloudy and it comes in fully corrected with the right profile: No clue why this wouldn't work correctly on your computer. Perhaps a hardware dependent bug. ... View more

Can you share a few raw files that this happens to? People here (and perhaps some Adobe folks) can try and follow along and see what the issue is. Upload to a cloud service such as Dropbox and share the link. ... View more

(note I am assuming you do not have the HDR option enabled in Develop) Any edited image in Lightroom is already tone mapped. The tools you use to do highlights, shadows, masks, etc are effectively ways to lower the dynamic range of an image into something that can be represented in a 8-bit image. So the equivalent of the HDR toning dialog box is simply the develop settings. If you can see the image on your typical display and it looks good, it is already ready to be exported to an 8-bit jpeg. ... View more

I have a similar M1 Max machine, same version of Classic but I run Mac OS 15.4.1 . This file denoises just fine on my machine both in Classic and in Lightroom Cloudy. Perhaps you need to update your mac os version. There were several GPU related fixes in the recent updates.  P.S. for screenshots one trick is to just type screenshot in the upper right hand corner looking glass icon. It will give you a built in screenshot utility that saves screenshots to your desktop. Very handy. ... View more

Ah. Yeah forget about anything you do in finder or what it shows on the icon, that has nothing to do with your issue. As Jim says, that is just the file type association in finder. It is annoying but Lightroom (classic clearly) does not care about any of that. What is going on here likely has more to do with your hardware and software. What version of Lightroom are you running? What computer hardware and what operating system version? Easiest is to post a result of "system info" from the help menu. ... View more